Add new extensions to conformance csv files #2096
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The extension tests in
test_conformance/extensions
have not matching entries in theopencl_conformance_tests_*.csv
files. This means that they are missed from conformance runs by vendors who use these files.I've included the new extensions in the full and quick CSV files as they don't have vast combinations of tests to run like bruteforce or conversions.
I've put
cl_khr_dx9_media_sharing
in thetest_conformance/opencl_conformance_tests_d3d.csv
CSV as like the other tests there the test binary is conditional built only on a Windows platform.I've created a new
opencl_conformance_tests_vulkan.csv
file for testing thecl_khr_external_semaphore
extension, as creation of the binary is conditional on the Vulkan SDK being enabled environment. Any other tests that require the Vulkan SDK in future can also be added there.